-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix active-active value #240
Conversation
/test all ✅ Terraform Azure Standalone Mounted Disk (FDO) - Test Report
✅ Terraform Azure Standalone Mounted Disk (Replicated) - Test Report
❌ Terraform Azure Standalone External (FDO) - Test Report
❌ Terraform Azure Standalone External (Replicated) - Test Report
❌ Terraform Azure Public Active/Active (FDO) - Test Report
✅ Terraform Azure Private TCP Active/Active (FDO) - Test Report
✅ Terraform Azure Public Active/Active (Replicated) - Test Report
✅ Terraform Azure Private Active/Active (Replicated) - Test Report
❌ Terraform Azure Private TCP Active/Active (Replicated) - Test Report
❌ Terraform Azure Private Active/Active (FDO) - Test Report
|
/destroy standalone-external ✅ Terraform Azure Standalone External (FDO) - Destruction Report
|
/destroy standalone-external-replicated ✅ Terraform Azure Standalone External (Replicated) - Destruction Report
|
/test private-active-active ✅ Terraform Azure Private Active/Active (FDO) - Test Report
|
/test private-tcp-active-active-replicated ✅ Terraform Azure Private TCP Active/Active (Replicated) - Test Report
|
/test public-active-active ✅ Terraform Azure Public Active/Active (FDO) - Test Report
|
Background
Jira TF-8610
Just noticed this error that I wanted to fix real quick. It ensures that the operational mode is Active/Active and not external if there are two or more nodes.
How Has This Been Tested
Below there are 10 passing tests, however, some of the destroys failed due to cloud provider issues so it looks messy. Here are the direct links to the passing tests:
FDO
Replicated